[#5318][#5311][#5328] improvement(web): Add jdbc-driver properties for Paimon JDBC and fix jdbc issue #5339
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…r Paimon JDBC and fix jdbc issue (#5320) ### What changes were proposed in this pull request? 1. Add jdbc-driver properties for Paimon JDBC <img width="589" alt="image" src="https://github.com/user-attachments/assets/fd8f5bf2-0f0a-4fbb-b6c5-5531c8d92155"> 3. fix update paimon catalog issue ### Why are the changes needed? Fix: #5318 Fix: #5311 Fix: #5328 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? manually
jerryshao
approved these changes
Oct 29, 2024
jerryshao
deleted the
cherry-pick-branch-0.7-fea1c740d184b37807c08eda4624c3d523afc4eb
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Why are the changes needed?
N/A
Fix: #5318
Fix: #5311
Fix: #5328
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
manually